-
Notifications
You must be signed in to change notification settings - Fork 375
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FATES API update for SPITFIRE refactor #6762
Conversation
This commit updates fates to API37 which is necessary to capture renaming per a fates-side fire refactor
Regression testing against |
Regression testing on This is good to integrate. |
notes: ready to go. |
Updates fates to API37 per a fates-side fire refactor which renames and moves `nfsc`. This updates the fates tag with a number of fates-side fixes and feature updates so fates tests will be answer changing. Fixes #6806 [non-B4B] for fates tests
@glemieux FATES tests did not show a DIFF when this PR was merged to next. Are there no FATES tests with SPITFIRE turned on? |
@bishtgautam most of the fates tests run with spitfire on. If they inherit the
I'm surprised that no diffs showed up in the merge to next, since I was seeing expected diffs per #6762 (comment). Is Just to clarify, I don't expect there to be diffs due to the spitfire refactor, but due to updating the fates tag which includes a number of interstitial fates updates. |
Yes e3sm_land_developer is included in e3sm_developer which is then included in e3sm_integration. |
@glemieux Perlmutter gnu is showing diffs on some FATES tests. Were you using gnu when you saw them? |
@rljacob sorry for the delayed response. Good clarification: Yes that's correct. I ran both
|
Updates fates to API37 per a fates-side fire refactor which renames and moves
nfsc
.This updates the fates tag with a number of fates-side fixes and feature updates so
fates tests will be answer changing.
Fixes #6806
[non-B4B] for fates tests